System and methods for dynamic scheduling in new radio with base station

ABSTRACT

Dynamic scheduling can be performed by 5G new radio in the licensed or unlicensed band. A base station can poll user equipment (UE) by transmitting a downlink control information (DCI) or other downlink communication that indicates resources that a UE can use to send a scheduling request. The resources are dynamic, e.g., they can be updated and allocated to UEs based on network conditions. Other aspects are described.

FIELD OF INVENTION

This invention relates generally to wireless technology and moreparticularly to dynamic scheduling in new radio (NR) and new radio inthe unlicensed spectrum (NR-U).

BACKGROUND OF THE INVENTION

Fifth generation mobile network (5G) is a wireless standard that aims toimprove upon data transmission speed, reliability, availability, andmore. This standard, while still developing, includes numerous detailsrelating to various aspects of wireless communication, for example, NRand NR in the unlicensed spectrum (greater than 52.6 GHz), also known asNR-U.

SUMMARY OF THE DESCRIPTION

Aspects of the present disclosure relate to 5G new radio (NR) operatingin the licensed band or in the unlicensed band (NR-U). 5G NR-U operatesabove the 52.6 GHz band.

In some aspects, a method or a device (e.g., user equipment or abaseband processor) configured to perform the method is described. Themethod can include receiving configuration information from a basestation, wherein the configuration information comprises information forfinding downlink control information (DCI); being polled by receivingthe DCI that includes indication of a physical uplink control channel(PUCCH) resource for the UE to transmit a dynamic scheduling request(SR); finding the DCI based on the configuration information; andtransmitting the dynamic SR in a PUCCH message based on the PUCCHresource, wherein uplink grant is performed based on the dynamic SR.

In some aspects, a method can include being polled by receiving adownlink control information (DCI) that includes a bit that instructsthe UE whether or not to send a dynamic scheduling request (SR); andtransmitting the dynamic SR in a PUCCH message based on a predeterminedphysical uplink control channel (PUCCH) resource configured in the UE,wherein uplink grant is performed based on the dynamic SR.

In some aspects, a method or network equipment (e.g., a base station orbaseband processor) that is configured to perform the method isdescribed. The method can include generating a downlink controlinformation (DCI) message containing an indication of a physical uplinkcontrol channel (PUCCH) resource for a UE to use to transmit a dynamicscheduling request (SR); polling the UE by transmitting the DCI thatincludes the PUCCH resource which is dynamically updated based on one ormore network conditions including network traffic, location of one ormore UE, or which of the one or more UE have data to transmit; receivingthe dynamic SR in a PUCCH message that is transmitted according to thePUCCH resource; and transmitting an uplink (UL) grant having beam andtime scheduling determined based on the dynamic SR.

In some aspects, a method includes generating a downlink controlinformation (DCI) that includes a bit that instructs a user equipment(UE) whether or not to send a dynamic scheduling request (SR); pollingthe UE by transmitting the DCI that includes the bit which isdynamically updated based on one or more network conditions includingnetwork traffic, location of one or more UE, or which of the one or moreUE have data to transmit; receiving the dynamic SR in a physical uplinkcontrol channel (PUCCH) message; and transmitting an uplink (UL) granthaving beam and time scheduling determined based on the dynamic SR.

Other methods and apparatuses are also described.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the figures of the accompanying drawings in which likereferences indicate similar elements.

FIG. 1 illustrates an example wireless communication system according tosome aspects.

FIG. 2 illustrates uplink and downlink communications according to someaspects.

FIG. 3 illustrates an example block diagram of a UE according to someaspects.

FIG. 4 illustrates an example block diagram of a BS according to someaspects.

FIG. 5 illustrates an example block diagram of cellular communicationcircuitry, according to some aspects.

FIG. 6 illustrates an example sequence for performing dynamic schedulingin NR or NR-U, according to some aspects.

FIG. 7 illustrates an example of dynamic scheduling resource signaling,according to some aspects.

FIG. 8 shows an example of a scheduling request that includes UEassistance information, according to some aspects.

FIG. 9 shows an example of a bit field used for dynamic schedulingrequest with semi-statically configured resources, according to someaspects.

FIG. 10 shows an example of scheduling requests with multiple UEs,according to some aspects.

FIG. 11 shows an example of dynamic scheduling request, according tosome aspects.

FIG. 12 shows dynamic scheduling with enforced time intervals betweencommunications, according to some aspects.

DETAILD DESCRIPTION

A method and apparatus of a device that determines a physical downlinkshared channel scheduling resource for a user equipment device and abase station is described. In the following description, numerousspecific details are set forth to provide thorough explanation ofaspects of the present invention. It will be apparent, however, to oneskilled in the art, that aspects of the present invention may bepracticed without these specific details. In other instances, well-knowncomponents, structures, and techniques have not been shown in detail inorder not to obscure the understanding of this description.

Reference in the specification to “some aspects” or “an aspect” meansthat a particular feature, structure, or characteristic described inconnection with the aspect can be included in at least one aspect of theinvention. The appearances of the phrase “in some aspects” in variousplaces in the specification do not necessarily all refer to the sameaspect.

In the following description and claims, the terms “coupled” and“connected,” along with their derivatives, may be used. It should beunderstood that these terms are not intended as synonyms for each other.“Coupled” is used to indicate that two or more elements, which may ormay not be in direct physical or electrical contact with each other,co-operate or interact with each other. “Connected” is used to indicatethe establishment of communication between two or more elements that arecoupled with each other.

The processes depicted in the figures that follow, are performed byprocessing logic that comprises hardware (e.g., circuitry, dedicatedlogic, etc.), software (such as is run on a general-purpose computersystem or a dedicated machine), or a combination of both. Although theprocesses are described below in terms of some sequential operations, itshould be appreciated that some of the operations described may beperformed in different order. Moreover, some operations may be performedin parallel rather than sequentially.

The terms “server,” “client,” and “device” are intended to refergenerally to data processing systems rather than specifically to aparticular form factor for the server, client, and/or device.

A method and apparatus of a device that determines a physical downlinkshared channel scheduling resource for a user equipment device and abase station is described. In some aspects, the device is a userequipment device that has a wireless link with a base station. In someaspects, the wireless link is a fifth generation (5G) link. The devicefurther groups and selects component carriers (CCs) from the wirelesslink and determines a virtual CC from the group of selected CCs. Thedevice additionally can perform a physical downlink resource mappingbased on an aggregate resource matching patterns of groups of CCs.

The frequency bands for 5G networks come in two sets—frequency range 1(FR1) and frequency range 2 (FR2). FR1 covers communications from 450MHz to 6 GHz, which includes the LTE frequency range. FR2 covers 24.25GHz to 52.6 GHz. FR2 is known as the millimeter wave (mmWave) spectrum.In some aspects, the UE and base station can communicate over NR in theunlicensed band which is above FR2, also known as NR-U.

NR-U is a mode of operation that defines technology for cellularoperators to integrate the unlicensed spectrum (e.g., frequenciesgreater than 52.6 GHz, such as, for example, between 52.6 GHz and 71GHz) into 5G networks. Radio waves in this band have wavelengths in theso-called millimeter band, and radiation in this band is known asmillimeter waves. NR-U enables both uplink and downlink operation inunlicensed bands. NR-U supports new features, for example, widebandcarriers, flexible numerologies, dynamic TDD, beamforming, and dynamicscheduling/HARQ timing.

In NR-U, license-assisted use as well as standalone use are supported inthe unlicensed spectrum. Operators can use a non-standalone mode toaggregate the unlicensed bands with licensed 5G frequencies to bolstercapacity (e.g., similar to LAA), as well as a standalone mode wherein anenterprise could use unlicensed spectrum to deploy a private cellularnetwork. It should be understood that aspects described in the presentdisclosure with reference to NR can also apply to NR-U and vice versaunless context dictates otherwise. Although NR-U has developed, problemsexist regarding dynamic scheduling, as are discussed in other sections.

FIG. 1 illustrates a simplified example wireless communication system,according to some aspects. It is noted that the system of FIG. 1 ismerely one example of a possible system, and that features of thisdisclosure may be implemented in any of various systems, as desired.

As shown, the example wireless communication system includes a basestation 102A which communicates over a transmission medium with one ormore user devices 106A, 106B, etc., through 106N. Each of the userdevices may be referred to herein as a “user equipment” (UE). Thus, theuser devices 106 are referred to as UEs or UE devices.

The base station (BS) 102A may be a base transceiver station (BTS) orcell site (a “cellular base station”) and may include hardware thatenables wireless communication with the UEs 106A through 106N.

The communication area (or coverage area) of the base station may bereferred to as a “cell.” The base station 102A and the UEs 106 may beconfigured to communicate over the transmission medium using any ofvarious radio access technologies (RATs), also referred to as wirelesscommunication technologies, or telecommunication standards, such as GSM,UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces),LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000(e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if the base station102A is implemented in the context of LTE, it may alternately bereferred to as an ‘eNodeB’ or ‘eNB’. Note that if the base station 102Ais implemented in the context of 5G NR, it may alternately be referredto as ‘gNodeB’ or ‘gNB’.

As shown, the base station 102A may also be equipped to communicate witha network 100 (e.g., a core network of a cellular service provider, atelecommunication network such as a public switched telephone network(PSTN), and/or the Internet, among various possibilities). Thus, thebase station 102A may facilitate communication between the user devicesand/or between the user devices and the network 100. In particular, thecellular base station 102A may provide UEs 106 with varioustelecommunication capabilities, such as voice, SMS and/or data services.

Base station 102A and other similar base stations (such as base stations102B . . . 102N) operating according to the same or a different cellularcommunication standard may thus be provided as a network of cells, whichmay provide continuous or nearly continuous overlapping service to UEs106A-N and similar devices over a geographic area via one or morecellular communication standards.

Thus, while base station 102A may act as a “serving cell” for UEs 106A-Nas illustrated in FIG. 1 , each UE 106 may also be capable of receivingsignals from (and possibly within communication range of) one or moreother cells (which might be provided by base stations 102B-N and/or anyother base stations), which may be referred to as “neighboring cells”.Such cells may also be capable of facilitating communication betweenuser devices and/or between user devices and the network 100. Such cellsmay include “macro” cells, “micro” cells, “pico” cells, and/or cellswhich provide any of various other granularities of service area size.For example, base stations 102A-B illustrated in FIG. 1 might be macrocells, while base station 102N might be a micro cell. Otherconfigurations are also possible.

In some aspects, base station 102A may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In someaspects, a gNB may be connected to a legacy evolved packet core (EPC)network and/or to a NR core (NRC) network. In addition, a gNB cell mayinclude one or more transition and reception points (TRPs). In addition,a UE capable of operating according to 5G NR may be connected to one ormore TRPs within one or more gNBs.

Note that a UE 106 may be capable of communicating using multiplewireless communication standards. For example, the UE 106 may beconfigured to communicate using a wireless networking (e.g., Wi-Fi)and/or peer-to-peer wireless communication protocol (e.g., Bluetooth,Wi-Fi peer-to-peer, etc.) in addition to at least one cellularcommunication protocol (e.g., GSM, UMTS (associated with, for example,WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). The UE 106 may alsoor alternatively be configured to communicate using one or more globalnavigational satellite systems (GNSS, e.g., GPS or GLONASS), one or moremobile television broadcasting standards (e.g., ATSC-M/H or DVB-H),and/or any other wireless communication protocol, if desired. Othercombinations of wireless communication standards (including more thantwo wireless communication standards) are also possible.

FIG. 2 illustrates UE 106A that can be in communication with a basestation 102 through uplink and downlink communications, according tosome aspects. The UEs may each be a device with cellular communicationcapability such as a mobile phone, a hand-held device, a computer or atablet, or virtually any type of wireless device.

The UE may include a processor that is configured to execute programinstructions stored in memory. The UE may perform any of the methodaspects described herein by executing such stored instructions.Alternatively, or in addition, the UE may include a programmablehardware element such as an FPGA (field-programmable gate array) that isconfigured to perform any of the method aspects described herein, or anyportion of any of the method aspects described herein.

The UE may include one or more antennas for communicating using one ormore wireless communication protocols or technologies. In some aspects,the UE may be configured to communicate using, for example, CDMA2000(1xRTT/1xEV-DO/HRPD/eHRPD) or LTE using a single shared radio and/or GSMor LTE using the single shared radio. The shared radio may couple to asingle antenna, or may couple to multiple antennas (e.g., for MIMO) forperforming wireless communications. In general, a radio may include anycombination of a baseband processor, analog RF signal processingcircuitry (e.g., including filters, mixers, oscillators, amplifiers,etc.), or digital processing circuitry (e.g., for digital modulation aswell as other digital processing). Similarly, the radio may implementone or more receive and transmit chains using the aforementionedhardware. For example, the UE 106 may share one or more parts of areceive and/or transmit chain between multiple wireless communicationtechnologies, such as those discussed above.

In some aspects, the UE may include separate transmit and/or receivechains (e.g., including separate antennas and other radio components)for each wireless communication protocol with which it is configured tocommunicate. As a further possibility, the UE may include one or moreradios which are shared between multiple wireless communicationprotocols, and one or more radios which are used exclusively by a singlewireless communication protocol. For example, the UE might include ashared radio for communicating using either of LTE or 5G NR (or LTE or1xRTTor LTE or GSM), and separate radios for communicating using each ofWi-Fi and Bluetooth. Other configurations are also possible.

FIG. 3 illustrates an example simplified block diagram of acommunication device 106, according to some aspects. It is noted thatthe block diagram of the communication device of FIG. 3 is only oneexample of a possible communication device. According to aspects,communication device 106 may be a UE device, a mobile device or mobilestation, a wireless device or wireless station, a desktop computer orcomputing device, a mobile computing device (e.g., a laptop, notebook,or portable computing device), a tablet and/or a combination of devices,among other devices. As shown, the communication device 106 may includea set of components 300 configured to perform core functions. Forexample, this set of components may be implemented as a system on chip(SOC), which may include portions for various purposes. Alternatively,this set of components 300 may be implemented as separate components orgroups of components for the various purposes. The set of components 300may be coupled (e.g., communicatively; directly or indirectly) tovarious other circuits of the communication device 106.

For example, the communication device 106 may include various types ofmemory (e.g., including NAND flash 310), an input/output interface suchas connector I/F 320 (e.g., for connecting to a computer system; dock;charging station; input devices, such as a microphone, camera, keyboard;output devices, such as speakers; etc.), the display 360, which may beintegrated with or external to the communication device 106, andcellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc.,and short to medium range wireless communication circuitry 329 (e.g.,Bluetooth™ and WLAN circuitry). In some aspects, communication device106 may include wired communication circuitry (not shown), such as anetwork interface card, e.g., for Ethernet.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 and 336 as shown. The short to medium range wirelesscommunication circuitry 329 may also couple (e.g., communicatively;directly or indirectly) to one or more antennas, such as antennas 337and 338 as shown. Alternatively, the short to medium range wirelesscommunication circuitry 329 may couple (e.g., communicatively; directlyor indirectly) to the antennas 335 and 336 in addition to, or insteadof, coupling (e.g., communicatively; directly or indirectly) to theantennas 337 and 338. The short to medium range wireless communicationcircuitry 329 and/or cellular communication circuitry 330 may includemultiple receive chains and/or multiple transmit chains for receivingand/or transmitting multiple spatial streams, such as in amultiple-input multiple output (MIMO) configuration.

In some aspects, as further described below, cellular communicationcircuitry 330 may include dedicated receive chains (including and/orcoupled to, e.g., communicatively; directly or indirectly. dedicatedprocessors and/or radios) for multiple radio access technologies (RATs)(e.g., a first receive chain for LTE and a second receive chain for 5GNR). In addition, in some aspects, cellular communication circuitry 330may include a single transmit chain that may be switched between radiosdedicated to specific RATs. For example, a first radio may be dedicatedto a first RAT, e.g., LTE, and may be in communication with a dedicatedreceive chain and a transmit chain shared with an additional radio,e.g., a second radio that may be dedicated to a second RAT, e.g., 5G NR,and may be in communication with a dedicated receive chain and theshared transmit chain.

The communication device 106 may also include and/or be configured foruse with one or more user interface elements. The user interfaceelements may include any of various elements, such as display 360 (whichmay be a touchscreen display), a keyboard (which may be a discretekeyboard or may be implemented as part of a touchscreen display), amouse, a microphone and/or speakers, one or more cameras, one or morebuttons, and/or any of various other elements capable of providinginformation to a user and/or receiving or interpreting user input.

The communication device 106 may further include one or more smart cards345 that include SIM (Subscriber Identity Module) functionality, such asone or more UICC(s) (Universal Integrated Circuit Card(s)) cards 345.

As shown, the SOC 300 may include processor(s) 302, which may executeprogram instructions for the communication device 106 and displaycircuitry 304, which may perform graphics processing and provide displaysignals to the display 360. The processor(s) 302 may also be coupled tomemory management unit (MMU) 340, which may be configured to receiveaddresses from the processor(s) 302 and translate those addresses tolocations in memory (e.g., memory 306, read only memory (ROM) 350, NANDflash memory 310) and/or to other circuits or devices, such as thedisplay circuitry 304, short range wireless communication circuitry 229,cellular communication circuitry 330, connector I/F 320, and/or display360. The MMU 340 may be configured to perform memory protection and pagetable translation or set up. In some aspects, the MMU 340 may beincluded as a portion of the processor(s) 302.

As noted above, the communication device 106 may be configured tocommunicate using wireless and/or wired communication circuitry. Thecommunication device 106 may also be configured to determine a physicaldownlink shared channel scheduling resource for a user equipment deviceand a base station. Further, the communication device 106 may beconfigured to group and select CCs from the wireless link and determinea virtual CC from the group of selected CCs. The wireless device mayalso be configured to perform a physical downlink resource mapping basedon an aggregate resource matching patterns of groups of CCs.

As described herein, the communication device 106 may include hardwareand software components for implementing the above features fordetermining a physical downlink shared channel scheduling resource for acommunications device 106 and a base station. The processor 302 of thecommunication device 106 may be configured to implement part or all ofthe features described herein, e.g., by executing program instructionsstored on a memory medium (e.g., a non-transitory computer-readablememory medium). Alternatively (or in addition), processor 302 may beconfigured as a programmable hardware element, such as an FPGA (FieldProgrammable Gate Array), or as an ASIC (Application Specific IntegratedCircuit). Alternatively (or in addition) the processor 302 of thecommunication device 106, in conjunction with one or more of the othercomponents 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processor 302 may include one or moreprocessing elements. Thus, processor 302 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor 302. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 302.

Further, as described herein, cellular communication circuitry 330 andshort range wireless communication circuitry 329 may each include one ormore processing elements. In other words, one or more processingelements may be included in cellular communication circuitry 330 and,similarly, one or more processing elements may be included in shortrange wireless communication circuitry 329. Thus, cellular communicationcircuitry 330 may include one or more integrated circuits (ICs) that areconfigured to perform the functions of cellular communication circuitry330. In addition, each integrated circuit may include circuitry (e.g.,first circuitry, second circuitry, etc.) configured to perform thefunctions of cellular communication circuitry 230. Similarly, the shortrange wireless communication circuitry 329 may include one or more ICsthat are configured to perform the functions of short range wirelesscommunication circuitry 32. In addition, each integrated circuit mayinclude circuitry (e.g., first circuitry, second circuitry, etc.)configured to perform the functions of short range wirelesscommunication circuitry 329.

FIG. 4 illustrates an example block diagram of a base station 102,according to some aspects. It is noted that the base station of FIG. 4is merely one example of a possible base station. As shown, the basestation 102 may include processor(s) 404 which may execute programinstructions for the base station 102. The processor(s) 404 may also becoupled to memory management unit (MMU) 440, which may be configured toreceive addresses from the processor(s) 404 and translate thoseaddresses to locations in memory (e.g., memory 460 and read only memory(ROM) 450) or to other circuits or devices.

The base station 102 may include at least one network port 470. Thenetwork port 470 may be configured to couple to a telephone network andprovide a plurality of devices, such as UE devices 106, access to thetelephone network as described above in FIGS. 1 and 2 .

The network port 470 (or an additional network port) may also oralternatively be configured to couple to a cellular network, e.g., acore network of a cellular service provider. The core network mayprovide mobility related services and/or other services to a pluralityof devices, such as UE devices 106. In some cases, the network port 470may couple to a telephone network via the core network, and/or the corenetwork may provide a telephone network (e.g., among other UE devicesserviced by the cellular service provider).

In some aspects, base station 102 may be a next generation base station,e.g., a 5G New Radio (5G NR) base station, or “gNB”. In such aspects,base station 102 may be connected to a legacy evolved packet core (EPC)network and/or to a NR core (NRC) network. In addition, base station 102may be considered a 5G NR cell and may include one or more transitionand reception points (TRPs). In addition, a UE capable of operatingaccording to 5G NR may be connected to one or more TRPs within one ormore gNBs. In some aspects, the base station can operate in 5G NR-Umode.

The base station 102 may include at least one antenna 434, and possiblymultiple antennas. The at least one antenna 434 may be configured tooperate as a wireless transceiver and may be further configured tocommunicate with UE devices 106 via radio 430. The antenna 434communicates with the radio 430 via communication chain 432.Communication chain 432 may be a receive chain, a transmit chain orboth. The radio 430 may be configured to communicate via variouswireless communication standards, including, but not limited to, 5G NR,5G NR-U, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

The base station 102 may be configured to communicate wirelessly usingmultiple wireless communication standards. In some instances, the basestation 102 may include multiple radios, which may enable the basestation 102 to communicate according to multiple wireless communicationtechnologies. For example, as one possibility, the base station 102 mayinclude an LTE radio for performing communication according to LTE aswell as a 5G NR radio for performing communication according to 5G NRand 5G NR-U. In such a case, the base station 102 may be capable ofoperating as both an LTE base station and a 5G NR base station. Asanother possibility, the base station 102 may include a multi-mode radiowhich is capable of performing communications according to any ofmultiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTEand Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

As described further subsequently herein, the BS 102 may includehardware and software components for implementing or supportingimplementation of features described herein. The processor 404 of thebase station 102 may be configured to implement or supportimplementation of part or all of the methods described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively, theprocessor 404 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit), or a combination thereof Alternatively (orin addition) the processor 404 of the BS 102, in conjunction with one ormore of the other components 430, 432, 434, 440, 450, 460, 470 may beconfigured to implement or support implementation of part or all of thefeatures described herein.

In addition, as described herein, processor(s) 404 may be comprised ofone or more processing elements. In other words, one or more processingelements may be included in processor(s) 404. Thus, processor(s) 404 mayinclude one or more integrated circuits (ICs) that are configured toperform the functions of processor(s) 404. In addition, each integratedcircuit may include circuitry (e.g., first circuitry, second circuitry,etc.) configured to perform the functions of processor(s) 404.

Further, as described herein, radio 430 may be comprised of one or moreprocessing elements. In other words, one or more processing elements maybe included in radio 430. Thus, radio 430 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof radio 430. In addition, each integrated circuit may include circuitry(e.g., first circuitry, second circuitry, etc.) configured to performthe functions of radio 430.

FIG. 5 illustrates an example simplified block diagram of cellularcommunication circuitry, according to some aspects. It is noted that theblock diagram of the cellular communication circuitry of FIG. 5 is onlyone example of a possible cellular communication circuit. According toaspects, cellular communication circuitry 330 may be included in acommunication device, such as communication device 106 described above.As noted above, communication device 106 may be a user equipment (UE)device, a mobile device or mobile station, a wireless device or wirelessstation, a desktop computer or computing device, a mobile computingdevice (e.g., a laptop, notebook, or portable computing device), atablet and/or a combination of devices, among other devices.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 a-b and 336 as shown (in FIG. 3 ). In some aspects,cellular communication circuitry 330 may include dedicated receivechains (including and/or coupled to, e.g., communicatively; directly orindirectly. dedicated processors and/or radios) for multiple RATs (e.g.,a first receive chain for LTE and a second receive chain for 5G NR). Forexample, as shown in FIG. 5 , cellular communication circuitry 330 mayinclude a modem 510 and a modem 520. Modem 510 may be configured forcommunications according to a first RAT, e.g., such as LTE or LTE-A, andmodem 520 may be configured for communications according to a secondRAT, e.g., such as 5G NR.

As shown, modem 510 may include one or more processors 512 and a memory516 in communication with processors 512. Modem 510 may be incommunication with a radio frequency (RF) front end 530. RF front end530 may include circuitry for transmitting and receiving radio signals.For example, RF front end 530 may include receive circuitry (RX) 532 andtransmit circuitry (TX) 534. In some aspects, receive circuitry 532 maybe in communication with downlink (DL) front end 550, which may includecircuitry for receiving radio signals via antenna 335 a.

Similarly, modem 520 may include one or more processors 522 and a memory526 in communication with processors 522. Modem 520 may be incommunication with an RF front end 540. RF front end 540 may includecircuitry for transmitting and receiving radio signals. For example, RFfront end 540 may include receive circuitry 542 and transmit circuitry544. In some aspects, receive circuitry 542 may be in communication withDL front end 560, which may include circuitry for receiving radiosignals via antenna 335 b.

In some aspects, a switch 570 may couple transmit circuitry 534 touplink (UL) front end 572. In addition, switch 570 may couple transmitcircuitry 544 to UL front end 572. UL front end 572 may includecircuitry for transmitting radio signals via antenna 336. Thus, whencellular communication circuitry 330 receives instructions to transmitaccording to the first RAT (e.g., as supported via modem 510), switch570 may be switched to a first state that allows modem 510 to transmitsignals according to the first RAT (e.g., via a transmit chain thatincludes transmit circuitry 534 and UL front end 572). Similarly, whencellular communication circuitry 330 receives instructions to transmitaccording to the second RAT (e.g., as supported via modem 520), switch570 may be switched to a second state that allows modem 520 to transmitsignals according to the second RAT (e.g., via a transmit chain thatincludes transmit circuitry 544 and UL front end 572).

As described herein, the modem 510 may include hardware and softwarecomponents for implementing the above features or for determining aphysical downlink shared channel scheduling resource for a userequipment device and a base station, as well as the various othertechniques described herein. The processors 512 may be configured toimplement part or all of the features described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively (or inaddition), processor 512 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 512, in conjunction with one or more of theother components 530, 532, 534, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 512 may include one or moreprocessing elements. Thus, processors 512 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 512. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 512.

As described herein, the modem 520 may include hardware and softwarecomponents for implementing the above features for determining aphysical downlink shared channel scheduling resource for a userequipment device and a base station, as well as the various othertechniques described herein. The processors 522 may be configured toimplement part or all of the features described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively (or inaddition), processor 522 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 522, in conjunction with one or more of theother components 540, 542, 544, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 522 may include one or moreprocessing elements. Thus, processors 522 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 522. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 522.

NR-U listen before talk (LBT) channel access mechanism can be based onED-based LBT of license assisted access (LAA). Two types of LBTs channelaccess mechanisms include a frame based equipment (FBE) access loadbased equipment (LBE) access. For FBE, a transmit/receive structure hasa periodic timing with a periodicity equal to the fixed frame period.For LBE, a transmit/receive structure is not fixed in time butdemand-driven. There are four categories of LBT that are defined in LAALBE operations which can be used as a baseline for NR-U. Category 1 isno LBT (i.e. immediate transmission). Category 2 is LBT without randombackoff. Category 3 is LBT with random backoff with fixed sizecontention window. Category 4 is LBT with random backoff with variablesize contention window.

After a successful LBT, an initiating device can access a channel atmost for a duration of a maximum channel occupancy time (MCOT). Sharingof channel occupancy time (COT) can be performed between an initiatingand responding node in any direction, such as, for example, gNB-acquiredCOT sharing and UE-acquired COT sharing. Two MCOT structures include LAAand NR-U. LAA has a single DL to UL switch. This provides for lessoverhead due to one single GP, and avoids multiple LBT. One setback hereis that larger latency may be present for HARQ-ACK feedback.

NR-U also supports multiple DL to UL switch and UL to DL switch. Thiscan result in reduced latency for delay-sensitive traffic, e.g. URLLC.In NR-U, if the gap between DL and UL or UL and DL is within 16 us (sameas SIFS in Wi-Fi), the transmission after the gap can occur withoutchannel sensing i.e. Cat-1 LBT. If the gap is larger than 16 us but lessthan 25 us, Cat-2 is allowed.

For initiation of a COT by the gNB (operating as a LBE device), thechannel access schemes in the table below can be used.

TABLE 1 Channel access schemes for gNB as LBE device Condition CAT 2 LBTCAT 4 LBT DRS alone or When the DRS duty cycle ≤1/20, When DRS dutycycle is >1/20, multiplexed with non-unicast and the total duration ortotal duration >1 ms, data (e.g. OSI, is up to 1 ms: 25 μs Cat 2 Cat 4with any channel access paging, RAR) LBT is used (as in LAA) priorityclass value can be used DRS multiplexed with N/A Channel access priorityclass unicast data is selected according to the multiplexed dataPhysical downlink control N/A Channel access priority class channel(PDCCH) and/or is selected according to the Physical downlink sharedmultiplexed data channel (PDSCH)

At least for the case where a DL burst follows a UL burst within agNB-initiated COT and there is no gap larger than 25 μs between any twotransmissions in the COT, the channel access schemes in the table belowapply.

TABLE 2 Channel access schemes for a DL burst follows a UL burst withina gNB-initiated COT as LBE device Cat 1 Immediate transmission Cat 2 LBTWhen the gap from the end of the When the gap from the end of thescheduled UL transmission to the scheduled UL transmission to thebeginning of the DL burst is up to beginning of the DL burst is larger16 μsec than 16 μsec but not more than 25 μsec

A DL/UL burst is defined as a set of transmissions from a given gNB/UEhaving no gaps or gaps of no more than 16 us. Transmissions from gNB/UEhaving a gap of more than 16 us are considered as separate DL/UL bursts.

Within a gNB-initiated COT, an UL burst for a UE consisting of one ormore of physical uplink shared channel (PUSCH), physical uplink controlchannel (PUCCH), physical random access channel (PRACH), and soundingreference signal (SRS) follows the channel access schemes in the tablebelow.

TABLE 3 Channel access schemes for a UL burst within a gNB-initiated Cat1 Immediate transmission Cat 2 LBT Cat 4 LBT When the gap from the endof For any of the following N/A the DL transmission to the cases:beginning of the UL burst is a) When the gap between any not more than16 msec. two successive scheduled/granted transmissions in the COT isnot greater than 25 msec b) For the case where a UL transmission in thegNB initiated COT is not followed by a DL transmission in the same COTNote: the duration from the start of the first transmission within thechannel occupancy until the end of the last transmission in the samechannel occupancy shall not exceed 20 ms.

For initiation of a COT by the UE, the channel access schemes in thebelow table can be used—using Cat-4 LBT for UCI-only PUSCH.

TABLE 4 Channel access schemes for initiating a COT by UE Cat 2 LBT Cat4 LBT PUSCH (including N/A except Channel access priority at leastUL-SCH for the cases class is selected with user plane discussed inaccording to the data data) Note 2 below SRS-only N/A Cat4 with lowestchannel access priority class value (as in LTE eLAA) RACH-only N/A Cat4with lowest channel access priority class value PUCCH-only (see Note 2)Cat4 with lowest channel access priority class value

Three different channel access mechanisms for Hybrid MAC for 60 GHzincludes CSMA/CA, TDMA, and polling. CSMA/CA is suitable for burstytraffic. Ideally CSMA/CA needs omni-directional transmit and receivebeams. In directional CSMA/CA, gNB is omni, and UE is directional. Inpaired CSMA/CA, UE switches beams for listen vs talk. For example,listen is omni, or in opposite direction). For 802.11ad. during theContention Based Access Period, enhanced 802.11 EDCA includes trafficcategories to support quality of service, frame aggregation and blockacknowledgments.

TDMA is suitable for large file transfer or wireless display, and/orwhen a UE is in non-interference region. Regarding 802.11ad with TDMA,service periods can be dedicated to a pair of communicating nodes. HCFis extended.

Polling can be performed in contention based period and service period.During polling, an AP pings each UE for data (directional SR), UEreplies (directional PUCCH), gNB schedules UE and UE transmits.Regarding 802.11ad and polling, Dynamic Channel Time Allocation is used.PCP/AP acquires medium, PCP/AP sends polling frames, STas send ServicePeriod Requests (SPRs), PCP/AP allocates time with grant frames.

Hybrid MAC can be a mix of all three channel access mechanisms. HybridMAC is used in 802.11ad.

Regarding channel access frame structure, a beacon interval can includea beacon header interval (BHI) and data transmission interval (DTI). TheBHI facilitates the exchange of management information and networkannouncements using a sweep of multiple directionally transmitted frame.In a BTI, a sector level sweep can be performed with multiple beaconframes (MCSO). In an Association Beamforming Training (A-BFT) timeslot,a responder sector level sweep (MCSO) can be performed. In anAnnouncement Transmission Interval (ATI), a PCP/AP exchanges managementinformation with an associated and beamtrained station (MCSx).

A DTI implements different types of medium access. Schedule can beannounced by PCP/AP. During the DTI, multiple contention based accessperiods (CBAP) can be performed using a variation of enhanceddistributed coordination function (EDCF). In some cases, rather thanCBAP, multiple service periods (SP): communication between a dedicatedpair of nodes in a contention free period. Dynamic channel allocationcan be supported through polling of STAs within CBAP or SP by PCP/AP anddynamic allocation of resources. In dynamic channel allocation, aschedule can be communicated by extended schedule element. In this case,pseudo-static access is used, the dynamic schedule recurs at the samerelative offset to target beacon transmission time (TBTT) and within thesame duration.

Scheduled/pseudo-static Contention Based Access can also be performed,such as CSMA/CA, for dynamic channel access. The schedule can be sent ina CBAP. The schedule can include traffic categories to support qualityof service, frame aggregation and block ACKs. This access methodsupports multiple NAV timers (one per peer STA), e.g., a transmissioncan be initiated with device if NAV for device is 0.

Scheduled/pseudo-static TMDA channel time allocation (TDMA) can beperformed. A schedule can be broadcast by PCP/AP in schedule elementnext to BTI or ATI. The schedule is sent in the Service Period (SP).This access method allows D2D transmission and supports multiple NAVtimers (one per peer STA) for protected mode transmission.

Dynamic channel time allocation (polling) can be performed. In such acase, STA can poll to receive SPR (Service Period Request). Time isallocated based on request using grant frames. This access method can beused in both CBAP (PCP/AP uses PIFS) and SP.

For periods of time that are scheduled by the AP/PCP, where any STA canaccess the channel, access during the CBAP is based on EDCA. All CBAPsare allocated by AP or PCP, except when allocated by a non-AP andnon-PCP STA with the transmission of a grant frame following an SPtruncation. There may be multiple CBAPs present in a beacon interval.PCP/AP may initiate a frame transmission within the CBAP immediatelyafter the medium is determined to be idle for one PIFS (8 usecs).Operation of EDCAF is suspend at the end of a CBAP and resumed atbeginning of following CBAP. The frame sent by the STA at the beginningof the TXOP may be an RTS frame or a DMG CTS-to-self frame.

Within a CBAP a STA with multiple DMG antennas should use only one DMGantenna in its frame transmission, CCA and frame reception, except if itis the initiator or responder in an SLS (10.42 (DMG beamforming)). Insuch a case, the algorithm to select a DMG antenna and switch the activeDMG antenna is implementation dependent. Within CBAPs a STA that changedto a different DMG antenna in order to transmit should perform CCA onthat DMG antenna until a frame is detected by which it can set its NAV,or until a period of time equal to the dot11DMGNavSync has transpired,whichever is earlier.

A service period can be negotiated between AP/PCP and STA or dynamicallyallocated, where only prescribed STAs can access the channel. Theservice period can be broadcast to multiple STAs, used for D2Dtransmission, dynamically extended beyond the allocated time in thecurrent SP in specific scenarios, and/or dynamically truncated torelease the remaining time in the SP (if truncatable)

Regarding service period recovery procedure; when a non-AP and non-PCPSTA fails to receive the extended schedule element for a beaconinterval, the non-AP and non-PCP STA has no knowledge of thenon-pseudo-static SPs allocated during the beacon interval that indicateit is the source DMG STA; therefore, it fails to transmit during thoseSPs. If the destination of the non-pseudo-static SP is an AP or PCP andit does not receive any frames from the source on-AP and non-PCP STA fora timeout interval, the AP/PCP may truncate the SP and reallocate theremaining duration of the SP to the source DMG STA of the SP or otherSTAs provided it is a truncatable SP. If not truncatable, it may stayawake or go into doze state. If non-AP/non-PCP STA does not receive anextended schedule element from the AP or PCP for that beacon interval,it may switch to doze state or may direct its receive antenna toward theAP or PCP to receive a grant during non-pseudo-static SPs or CBAPs inthe current beacon interval.

A protected period can be enforced to minimize interference betweenpairs of communicating STAs. This protected period can be enforced bylimiting the transmission of frames during the DMG protected period tonot more than one pair of potentially interfering pairs of communicatingstations. Dynamic BW operation to can be used to negotiate BW to be usedby this SP. STA can be set to listening mode for an interval before SPand only transmit if clear (CAT2 type access). In this case, antennasare in Quasi-omni mode or directed towards peer DMG STA. The protectedperiod can be established through a RTS/DMG CTS handshake. Interferencecan be reported to PCP/AP.

Dynamic allocation of a service period can be employed to allocatechannel time during scheduled SPs and CBAPs. The dynamic allocation caninclude an optional polling period (PP) phase and a grant period (GP)phase.

Regarding channel access intervals, before BI, CAT 4 applies. Within BTIand A-BFT, fixed intervals apply. In such a case, the MBIFS shall beused between the BTI and the A-BFT and between the ISS, RSS,SSW-Feedback, and SSW-Ack. MBIFS is equal to 3×aSIFSTime. A-BFT can beslotted with MBIFS between packets in a slot. Between A-BFT and ATI thelarger of (guard time, MBIFS) applies. Within ATI, once the ATI starts,the AP or PCP may start transmission of a request frame immediately orit may delay the transmission of the request frame if the medium isdetermined by the CCA mechanism to be busy. Response is SIFS fromrequest frame. Source initiates at start of SP except if protectedperiod needs to be established i.e. listens to medium based on RTS/DMGCTS transmission. A reply (SIFS) and/or retransmit (PIFS) can beperformed in SP. In CBAP, CAT4 applies. For PCP/AP or other sources,PIFS applies. For polling SBIFS and/or SIFS is used.

For communications (e.g., 5G-NRU) that operate at >52.6 GHz, it may bedesirable for a gNB to perform a dynamic polling of all the UEs toidentify which UEs have data and modify its resource allocationaccordingly. This allows flexible reassignment of time and beamresources in mmWave transmission.

Satisfactory communications could require beams in direction of UE. Dueto beam based allocation, a UE may only be able to send an SRdynamically only when its beam pair is active. If dynamic change in beampair, UE may not know if beam is active to send SR and request forresources. Statically allocate resources, in this case, may bedeficient. Thus, communications can benefit from a dynamic SR in an NRor NR-U environment.

A SR that uses a PRI in the DCI to indicate a set of semi-staticallyconfigured PUCCH resources identified by a first symbol, a number ofsymbols and other parameters may lack flexibility. Additionalflexibility may be needed to indicate the PUCCH resource(s) relative tothe DCI and appropriate signaling within the DCI. Thus, a dynamic SRconfiguration may provide improved flexibility.

Overhead of signaling the presence of an SRI in a DCI can be high ifPUCCH resources are dynamically changed and DCI is used to signal thePUCCH resource. To reduce overhead, in some aspects, PUCCH resourcesignaling for Dynamic SR can be part of an existing DCI transmission. Insome aspects, dedicated PUCCH resource signaling for Dynamic SR. In someaspects, a semi-static configuration can reduce overhead.

Based on LBT failure, a methodology could be required to enable reliablePUCCH and PUSCH transmission. For example, multiple PUCCH resources canbe signaled. To communicate over PUSCH, additional information may alsobe needed in the SR feedback to enable the gNB identify the bestresource to send information in e.g. beam, CC, or BWP. Multipleresources can be signaled for PUSCH transmission.

In some aspects, with signaling of dynamic resources, there may betimeline issues. Time gaps may be enforced between signaling. The gapcan be determined based on the number of beams and/or processing time.

Referring to FIG. 6 , dynamic scheduling is shown according to someaspects. The dynamic scheduling can be performed over 5G NR or 5G NR-U.

At operation 602, the base station can transmit configurationinformation to a user equipment (UE) that indicates how to find a DCI.The configuration information describes where the DCI is located (e.g.,a location within a COT allocated to the base station).

In some aspects, the configuration information defines a search space(SS) that the UE can use to locate the DCI (e.g., within a COT). Thesearch space can be an area (e.g., defined as a block of time or data)in a downlink resource defined for a UE to perform blind decoding to tryto find data (e.g., a DCI).

In some aspects, the search space is defined as fixed relative to astart of the COT. For example, the search space can be defined as being‘x’ number of resource blocks that begins ‘y’ symbols after thebeginning of a COT. In some aspects, the search space can be defined aspart of downlink burst signaling. For example, the search space can bedefined as a group common physical downlink control channel (GC-PDCCH)COT in time/frequency domain structure.

In some aspects, rather than define a search space, the configurationinformation can specify a precise location of the DCI. The receiving UEis configured with the exact location of the DCI in a receivedtransmission to decode the DCI accordingly. In some aspects,configuration information can define the DCI as positioned relative tonumerology. For example, the DCI can be defined as having a locationrelative to specific resource blocks and symbols. A symbol can be anOFDM symbol describing a time slot in a frequency band for a particularchannel. Numerology refers to the configuration of waveform parameters.Different numerologies can be considered as OFDM-based sub-frames havingdifferent parameters such as subcarrier spacing/symbol time, CP size,etc.

In some aspects, the configuration information defines the DCI messageas positioned relative to a start of the COT. For example, the DCImessage can be defined in the configuration information as being ‘x’number of resource blocks ‘y’ symbols fixed relative to the beginning ofthe COT. In some aspects, configuration information defines the DCI asbeing part of downlink burst signaling. For example, the DCI locationcan be defined in the configuration information as being located in agroup common physical downlink control channel (GC-PDCCH) COT intime/frequency domain structure.

The UE can receive the configuration information from the base station,that includes details as to how to find the DCI message (e.g., in aCOT).

At operation 603, a base station can request network resources, such asa channel occupancy time (COT) or maximum channel occupancy time (MCOT)of a channel, from a network. The network can determine the COT or MCOTto be allocated for the base station, and at operation 604 send aresponse to the base station that includes COT or MCOT. In some aspects,the resource request 603 is performed through a contention-basedprotocol (e.g., LBT). In some aspects, the network resources arestatically configured, e.g., the base station has a statically assignedchannel and time. The network can include a mix of network devices thatshare bandwidth over common frequencies.

At operation 604, the network can send a response to the base stationthat allocates channel resources. For example, the response can define aCOT or MCOT with which the base station is free to use a channel. Itshould be understood that operation 602 can occur before and/or afteroperations 603 and 604.

At operation 616, the base station can generate a DCI. The DCI canindicate to each of the one or more UEs what PUCCH resources should beused by a UE to send a dynamic SR. The PUCCH resource can include asymbol (e.g., 10, 16, 18), that defines to the UE and base station whichbeam pair and/or time the dynamic SR will be communicated over. ThePUCCH resources can be dynamically updated based on one or more networkconditions including network traffic, location of one or more UE, orwhich of the one or more UE have data to transmit. Details of the PUCCHresource are discussed in other sections. The DCI can have a format 2_0,2_1, 2_2, or other downlink DCI format currently existing or developedin the future.

At operation 606, the base station can poll the UE by transmitting a DCIcan be to one or more UEs (such as the one shown in FIG. 6 ). The PUCCHresources that are associated with each of the one or more UEs, whichare indicated in the DCI, can change over time based on networkconditions. The DCI transmissions can be performed periodically, orwhenever a change to the network conditions occurs which can prompt achange to the allocation of PUCCH resources to the one or more UEs.

At operation 618, the UE can receive/decode the DCI, and find the DCIbased on the configuration information received at operation 602, asdescribed in other sections. The UE can decode the DCI to determine thePUCCH resource to be used to send the dynamic SR.

The PUCCH resource can be signaled to the UE in different ways. In someaspects, the DCI includes a PUCCH resource indicator (PRI) having a bitfield that indicates the PUCCH resource to be used for the dynamic SR.The PUCCH resource can be a 3-bit indicator that is included as part ofthe DCI, which can have format 1_0 or 1_1. PUCCH resources for HARQ aretypically signaled as part of DCI format 1_1 in the PRI (which can be 3bits). A new field may be added, or an additional bit may be added(e.g., to form a 4 bit PRI) to indicate whether the PRI is associatedwith hybrid automatic repeat request (HARQ) or dynamic SR. In someaspects, rather than having separate PUCCH resources for HARQ anddynamic SR, the dynamic SR can be multiplexed with a HARQ transmission.

Understanding that PUCCH resources may be needed for both HARQ and SR,and that PUCCH resources may be semi-statically configured to identifyan absolute first symbol location, a number of symbols and otherparameters, there are some options below that can use new table(different from the semi-statically configured look-up) or a subset ofthe semi-statically configured look-up.

In some aspects, the UE finds the PUCCH resource based on a) a resourcelookup different from a semi-static PUCCH lookup, and b) a relativefirst symbol location that is relative to a position of the PRI in theDCI. For example, if the PRI is received in symbol n and indicates arelative first symbol location x, the PUCCH resource can be in or startfrom the symbol (n+x).

In some aspects, the UE finds the PUCCH resource based on a) a subset ofa semi-static PUCCH lookup, and b) a relative first symbol location thatis relative to a position of the PRI in the DCI. For example, if the PRIis received in symbol n and indicates a relative first symbol locationx, the PUCCH resource can be in or start from the symbol (n+x). Thesubset may be the first m entries of the table or a configured sub-setof m entries of the table.

In some aspects, the dynamic SR includes or is multiplexed with channelstate information (CSI). CSI is a mechanism that allows the UE to reportmeasured radio channel quality to the base station.

In some aspects, the PUCCH resource signaling is performed by assigninga CRC or a scrambled CRC to a UE. The CRC or scrambled CRC can beassigned to one or more UEs. For example, the CRC can be scrambled withdemodulation reference signal (DRS) radio network temporary identifier(RNTI) and the RNTI can be assigned to the UE. The CRC or scrambled CRCcan indicate to the UE which bit-field in a DCI carries a PUCCH resourceindicator for that UE. A single DCI can carry multiple UE-dedicated bitfields, each of which carry PUCCH resource for dynamic SR transmissionfor the corresponding UE.

For example, referring to FIG. 7 , the UE (e.g., UE(N)) is one of aplurality of UEs, and the DCI includes a plurality of bit fields, eachbit field being assigned to a corresponding one of the one or more UE.The PUCCH resource (e.g., one or more symbols) for the UE to use fortransmitting the dynamic SR is indicated in the bit field assigned tothe UE.

In some aspects, each bit field can be assigned to the corresponding oneof the one or more UE based on a radio network temporary identifier(RNTI). For example, a check record sum of the entire DCI or each bitfield is scrambled with RNTI, and each RNTI is assigned to each of theone or more UE.

Each RNTI can be used by the UE to find the bit field that is assignedto a UE. A starting position and number of bits (e.g., if the size isvariable) of each of the plurality of bit fields can be semi-staticallyconfigured. In some aspects, the starting position alone is enough(e.g., if the size bit field is not variable). The PUCCH resource forthe UE is indicated in one of the plurality of bit fields (e.g., as avalue), and PUCCH resources for others of the plurality of UEs arelocated in others of the plurality of bit fields. In some aspects, a bitfield dedicated to a single UE can signal more than one PUCCH resourcein case there may be an LBT failure of the single resource. In someaspects, the DCI has a format of 2_6 or a group common DCI.

Upon successful decoding of the PUCCH resource (e.g., the PUCCH resourceis found by the UE), the UE may send a dynamic SR in the specified PUCCHresource. If decoding of the PUCCH resource is unsuccessful (e.g., theUE cannot find the PUCCH resource), then the UE can decline to send thedynamic SR.

Referring back to FIG. 6 , at operation 608, the UE can transmit thedynamic SR in a PUCCH message based on the PUCCH resource that wasindicated in the DCI. For example, the PUCCH resource can include asymbol (e.g. 10, 16, 18), that defines to the UE and gNB which beam pairand/or time the dynamic SR will be communicated over. The SR iscommunicated over a PUCCH message as defined by the symbol (e.g., at aparticular time using a particular beam pair). Symbol format and PUCCHformat can vary based on application.

In some aspects, the dynamic SR that is transmitted from the UE to thebase station can include PUCCH signaling for increased reliability. Thiscan be used to assist the base station in determining resources for datatransfer.

For example, as shown in FIG. 8 , the UE may include, in the dynamic SR,additional information (e.g., UE assistance for LBT) to enable the gNBto identify an improved resource to send information in the schedulingphase. This can include, for example, a beam, a listen before talk (LBT)band, a time slot to transmit, and bandwidth parts (BWPs). In someaspects, the UE sends the dynamic SR only if the UE wishes to reserve aslot and/or has data to send to the base station and/or has successfullyfound and decoded the PUCCH resource.

At operation 620, the base station can process the SR to determine whichresources the uplink transmission will use. In other words, the basestation determines which PUSCH resource that the UE will use for the ULtransmission of data. This determination can be based on networktraffic, SR requests from other UEs (that can be used to scheduletraffic to and from multiple UEs), and information (e.g., UE assistancefor LBT) that was sent back from the UE in the dynamic SR request atoperation 608.

At oration 610, the base station can send an UL grant to the userequipment, which can be a scheduling DCI (e.g., format 0_X). Atoperation 612, the UE can transmit UL data to the base station, over ULresources that are specified in the UL grant.

In some aspects, the DCI resource and the corresponding dynamic SRresource (e.g., the PUCCH resource) may be semi-statically configuredtogether. In this case, a single bit (or a field of bits where each bitcorresponds to a particular UE) may be configured to indicate if the UEshould send a dynamic SR in a predetermined resource. The bit or fieldof bits can be transmitted by the base station to one or more UEs, anddynamically updated (e.g., from one time to another, and/or betweenperiodic transmissions of the DCI) based on one or more networkconditions including network traffic, location of one or more UE, orwhich of the one or more UE have data to transmit or changes thereof.

For example, referring to FIG. 9 a bit field 900 is shown, which can beincluded in the DCI (or other suitable downlink communication), canindicate to one or more UEs whether or not each of the one or more UEsshould transmit a dynamic SR. In this case, rather than including thePUCCH resource in the DCI, the PUCCH resource is semi-staticallyconfigured. In some aspects, the bit field need not be carried in DCI,but can be carried in another suitable downlink communication from thebase station the UE. In other words, where the dynamic SR resources aresemi-statically configured, operation 602 of FIG. 6 can be bypassed, andoperation 606 need not include a polled DCI, but can be any suitabledownlink communication carrying the described bit-field. The UE need notfind the PUCCH resource because the UE will ‘know’ which PUCCH resourceto use for the dynamic SR based on the semi-static configuration. Forexample, the base station can configure the UE to use symbol 10. So longas the bit corresponding to the UE is set in a received poll, the UEwill send a dynamic SR using symbol 10.

It should be understood that semi-static configuration can be performedthrough radio resource control (RRC) communications between a basestation and a UE (e.g., from a base station to the UE, and vice versa).RRC protocol can include connection establishment and release functions,broadcast of system information, radio bearer establishment,reconfiguration and release, RRC connection mobility procedures, pagingnotification and release and outer loop power control. By means of thesignaling functions, the RRC configure a UE (e.g., semi-statically).

FIG. 10 shows an example of SR scheduling with multiple UEs. Duringpolling period 1001, a base station can poll N number of UEs. Some orall of the UEs can respond with a corresponding SR. During a grantperiod 1002, the base station can transmit UL grants (e.g., in the formof a scheduling DCI) to the UEs. UL transmission can be performed duringdata transfer period 1003.

FIG. 11 shows a flow diagram of dynamic scheduling, according to someaspects. DCI configuration can be sent from the base station to the UEat block 1101. This tells the UE how to find the DCI or where to expectto find the DCI. The DCI is sent to the UE at block 1102. At block 1103,the dynamic SR is sent from the UE to the base station. At block 1104, aUL grant is sent from the base station to the UE and data is sent fromthe UE to the base station.

Referring to FIG. 12 shows a flow diagram of dynamic scheduling similarto FIG. 11 , however, in this case, due to beam switching and processingtimes, a minimum time interval can be enforced between the elements ofthe dynamic scheduling (e.g., the DCI, dynamic SR, scheduling DCI and/ortransmission). Thus, a time interval can be enforced between some of thecommunications between the UE and the base station (e.g., betweenreceiving the DCI and transmitting the dynamic SR, or between receivingthe dynamic SR and transmitting the UL grant). The time interval can begreater than or equal to a larger of a) a time required to change fromone beam to another (e.g., of the UE and/or the base station), or b) aprocessing time (e.g., of the UE).

The processing time either be fixed to a value based on 120 kHz, ormodified to account for new sub carrier spacing (SCS) values (e.g., 240kHz, 480 kHz, 960 kHz, etc.). The beam switching time may be based onexisting beam switching time limits (e.g., of a UE). The gNB mayschedule each element of the procedure in groups. This scheduling may betransparent to the UE. In some aspects, for 120 kHz, tproc2=20 symbols.As such, the interval between DCI and dynamic SR should be at least 20symbols.

Portions of what was described above may be implemented with logiccircuitry such as a dedicated logic circuit or with a microcontroller orother form of processing core that executes program code instructions.Thus processes taught by the discussion above may be performed withprogram code such as machine-executable instructions that cause amachine that executes these instructions to perform certain functions.In this context, a “machine” may be a machine that converts intermediateform (or “abstract”) instructions into processor specific instructions(e.g., an abstract execution environment such as a “virtual machine”(e.g., a Java Virtual Machine), an interpreter, a Common LanguageRuntime, a high-level language virtual machine, etc.), and/or,electronic circuitry disposed on a semiconductor chip (e.g., “logiccircuitry” implemented with transistors) designed to executeinstructions such as a general-purpose processor and/or aspecial-purpose processor. Processes taught by the discussion above mayalso be performed by (in the alternative to a machine or in combinationwith a machine) electronic circuitry designed to perform the processes(or a portion thereof) without the execution of program code.

The present invention also relates to an apparatus for performing theoperations described herein. This apparatus may be specially constructedfor the required purpose, or it may comprise a general-purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program may be stored in a computerreadable storage medium, such as, but is not limited to, any type ofdisk including floppy disks, optical disks, CD-ROMs, andmagnetic-optical disks, read-only memories (ROMs), RAMs, EPROMs,EEPROMs, magnetic or optical cards, or any type of media suitable forstoring electronic instructions, and each coupled to a computer systembus.

A machine readable medium includes any mechanism for storing ortransmitting information in a form readable by a machine (e.g., acomputer). For example, a machine readable medium includes read onlymemory (“ROM”); random access memory (“RAM”); magnetic disk storagemedia; optical storage media; flash memory devices; etc.

A baseband processor (also known as baseband radio processor, BP, orBBP) is a device (a chip or part of a chip) in a network interface thatmanages radio functions, such as communicating (e.g., TX and RX) over anantenna.

An article of manufacture may be used to store program code. An articleof manufacture that stores program code may be embodied as, but is notlimited to, one or more memories (e.g., one or more flash memories,random access memories (static, dynamic or other)), optical disks,CD-ROMs, DVD ROMs, EPROMs, EEPROMs, magnetic or optical cards or othertype of machine-readable media suitable for storing electronicinstructions. Program code may also be downloaded from a remote computer(e.g., a server) to a requesting computer (e.g., a client) by way ofdata signals embodied in a propagation medium (e.g., via a communicationlink (e.g., a network connection)).

The preceding detailed descriptions are presented in terms of algorithmsand symbolic representations of operations on data bits within acomputer memory. These algorithmic descriptions and representations arethe tools used by those skilled in the data processing arts to mosteffectively convey the substance of their work to others skilled in theart. An algorithm is here, and generally, conceived to be aself-consistent sequence of operations leading to a desired result. Theoperations are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be kept in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the above discussion, itis appreciated that throughout the description, discussions utilizingterms such as “selecting,” “determining,” “receiving,” “forming,”“grouping,” “aggregating,” “generating,” “removing,” or the like, referto the action and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (electronic) quantities within the computer system's registersand memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission or display devices.

The processes and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general-purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct a more specializedapparatus to perform the operations described. The required structurefor a variety of these systems will be evident from the descriptionbelow. In addition, the present invention is not described withreference to any particular programming language. It will be appreciatedthat a variety of programming languages may be used to implement theteachings of the invention as described herein.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

The foregoing discussion merely describes some exemplary aspects of thepresent invention. One skilled in the art will readily recognize fromsuch discussion, the accompanying drawings and the claims that variousmodifications can be made without departing from the spirit and scope ofthe invention.

What is claimed is:
 1. A method performed by network equipment in a 5Gnew radio (NR) in a licensed or an unlicensed spectrum environment,comprising: generating a downlink control information (DCI) messagecontaining an indication of a physical uplink control channel (PUCCH)resource for a UE to use to transmit a dynamic scheduling request (SR);polling the UE by transmitting the DCI that includes the PUCCH resourcewhich is dynamically updated based on one or more network conditionsincluding network traffic, location of one or more UE, or which of theone or more UE have data to transmit; receiving the dynamic SR in aPUCCH message that is transmitted according to the PUCCH resource; andtransmitting an uplink (UL) grant determined based on the dynamic SR. 2.The method of claim 1, wherein the DCI is transmitted over a channelduring a specified channel occupancy time (COT).
 3. (canceled) 4.(canceled)
 5. (canceled)
 6. (canceled)
 7. The method of claim 1, furthercomprising transmitting configuration information to a user equipment(UE) that indicates how to find the DCI, wherein the configurationinformation defines the DCI as positioned relative to numerology.
 8. Themethod of claim 1, further comprising transmitting configurationinformation to a user equipment (UE) that indicates how to find the DCI,wherein the configuration information defines the DCI as being part ofdownlink burst signaling.
 9. The method of claim 1, wherein the DCIincludes a PUCCH resource indicator (PRI) having a bit field thatindicates the PUCCH resource to be used for the dynamic SR. 10.(canceled)
 11. (canceled)
 12. (canceled)
 13. (canceled)
 14. (canceled)15. (canceled)
 16. (canceled)
 17. (canceled)
 18. (canceled) 19.(canceled)
 20. (canceled)
 21. (canceled)
 22. (canceled)
 23. (canceled)24. (canceled)
 25. (canceled)
 26. (canceled)
 27. (canceled) 28.(canceled)
 29. (canceled)
 30. (canceled)
 31. (canceled)
 32. A basestation comprising a processor (or processing circuitry) configured toperform operations comprising: generating a downlink control information(DCI) message containing an indication of a physical uplink controlchannel (PUCCH) resource for a UE to use to transmit a dynamicscheduling request (SR); polling the UE by transmitting the DCI thatincludes the PUCCH resource which is dynamically updated based on one ormore network conditions including network traffic, location of one ormore UE, or which of the one or more UE have data to transmit; receivingthe dynamic SR in a PUCCH message that is transmitted according to thePUCCH resource; and transmitting an uplink (UL) grant determined basedon the dynamic SR.
 33. (canceled)
 34. (canceled)
 35. (canceled) 36.(canceled)
 37. (canceled)
 38. (canceled)
 39. (canceled)
 40. (canceled)41. (canceled)
 42. (canceled)
 43. (canceled)
 44. The base station ofclaim 32, wherein the dynamic SR is multiplexed with a hybrid automaticrepeat request (HARQ) transmission.
 45. (canceled)
 45. (canceled) 46.The base station of claim 32, wherein the UE is one of the one or moreUE, and the DCI includes a plurality of bit fields, each bit field beingassigned to a corresponding one of the one or more UE.
 47. (canceled)48. (canceled)
 49. (canceled)
 50. (canceled)
 51. (canceled) 52.(canceled)
 53. The base station of claim 32, wherein UL resourcesincluding beam and time scheduling that are include in the UL grant isdetermined based on information contained in the dynamic SR includingone or more of: a beam, a listen before talk (LBT) band, a time slot totransmit, and bandwidth parts (BWPs).
 54. The base station of claim 32,wherein a time interval is enforced between receiving the dynamic SR andtransmitting the UL grant to be greater than or equal to a larger of a)a time required to change from one beam to another, or b) a processingtime.
 55. (canceled)
 56. (canceled)
 57. (canceled)
 58. (canceled) 59.(canceled)
 60. (canceled)
 61. (canceled)
 62. (canceled)
 63. A basebandprocessor, configured to perform operations comprising: generating adownlink control information (DCI) message containing an indication of aphysical uplink control channel (PUCCH) resource for a UE to use totransmit a dynamic scheduling request (SR); polling the UE bytransmitting the DCI that includes the PUCCH resource which isdynamically updated based on one or more network conditions includingnetwork traffic, location of one or more UE, or which of the one or moreUE have data to transmit; receiving the dynamic SR in a PUCCH messagethat is transmitted according to the PUCCH resource; and transmitting anuplink (UL) grant determined based on the dynamic SR.
 64. The basebandprocessor of claim 63, wherein the DCI is transmitted over a channelduring a specified channel occupancy time (COT). 65-68. (canceled) 69.The baseband processor of claim 63, the operations further comprisingtransmitting configuration information to a user equipment (UE) thatindicates how to find the DCI, wherein the configuration informationdefines the DCI as positioned relative to numerology.
 70. The basebandprocessor of claim 63, the operations further comprising transmittingconfiguration information to a user equipment (UE) that indicates how tofind the DCI, wherein the configuration information defines the DCI asbeing part of downlink burst signaling.
 71. The baseband processor ofclaim 63, wherein the DCI includes a PUCCH resource indicator (PRI)having a bit field that indicates the PUCCH resource to be used for thedynamic SR. 72-74. (canceled)
 75. The baseband processor of claim 63,wherein the dynamic SR is multiplexed with a hybrid automatic repeatrequest (HARQ) transmission.
 76. The baseband processor of claim 63,wherein the dynamic SR includes channel state information (CSI). 77-82.(canceled)
 83. The baseband processor of claim 63, wherein the UEtransmits the dynamic SR if the PUCCH resource is successfully found,but does not transmit the dynamic SR if the PUCCH resource is notsuccessfully found.
 84. The baseband processor of claim 63, wherein ULresources including beam and time scheduling that are included in the ULgrant are determined based on information contained in the dynamic SRincluding one or more of: a beam, a listen before talk (LBT) band, atime slot to transmit, and bandwidth parts (BWPs).
 85. The basebandprocessor of claim 63, wherein a time interval is enforced betweenreceiving the dynamic SR and transmitting the UL grant to be greaterthan or equal to a larger of a) a time required to change from one beamto another, or b) a processing time. 86-93. (canceled)